System and method of cryptographically signing web applications

ABSTRACT

Embodiments disclosed herein provide a method that includes receiving, at a client-side web browser, a minimal bootstrap payload from an application server; storing, by a client-side processor, the minimal bootstrap payload in a client-side local cache, where the locally cached minimal bootstrap payload is executed by the client-side processor before executing an application from the application server; the minimal bootstrap payload includes at least one public key and at least one Uniform Resource Location (URL) address of an application code payload.

CROSS-REFERENCE TO RELATED APPLICATIONS

This application is a Continuation of U.S. Ser. No. 16/152,876, filedOct. 5, 2018; which is a Continuation of U.S. Ser. No. 15/673,884, filedAug. 10, 2017, now U.S. Pat. No. 10,097,357; which is a Continuation ofU.S. Ser. No. 15/001,015, filed Jan. 19, 2016, now U.S. Pat. No.9,906,369; which is a Continuation of International Application No.:PCT/US15/47788, filed Aug. 31, 2015; which claims priority to U.S.Provisional Application No. 62/104,307, entitled “SYSTEM AND METHOD OFCRYPTOGRAPHICALLY SIGNING WEB APPLICATIONS” and filed Jan. 16, 2015; andfurther claims priority to U.S. Non-Provisional application Ser. No.15/001,015, entitled “SYSTEM AND METHOD OF CRYPTOGRAPHICALLY SIGNING WEBAPPLICATIONS” and filed Jan. 19, 2016.

The subject matter of the present application is related to thatdisclosed in the following co-pending applications:

Ser. No. 14/841,327, entitled “CROSS-CLIENT COMMUNICATION METHOD” andfiled Aug. 31, 2015 and claiming priority to U.S. ProvisionalApplication No. 62/100,674 filed on Jan. 7, 2015;

Ser. No. 14/841,318, entitled “CRYPTOGRAPHIC METHOD FOR SECURECOMMUNICATIONS” and filed Aug. 31, 2015 and claiming priority to U.S.Provisional Application No. 62/100,676, filed on Jan. 7, 2015;

Ser. No. 14/841,313, entitled “METHOD OF DENIABLE ENCRYPTEDCOMMUNICATIONS” and filed Aug. 31, 2015 and claim g priority to U.S.Provisional Application No. 62/100,682, filed on Jan. 7, 2015;

Ser. No. 14/841,281, entitled “ENCRYPTED GROUP COMMUNICATION METHOD” andfiled Aug. 31, 2015 and claiming priority to U.S. ProvisionalApplication No. 62/100,684, filed on Jan. 7, 2015;

Ser. No. 14/841,310, entitled “METHOD OF GENERATING A DENIABLE ENCRYPTEDCOMMUNICATIONS VIA PASSWORD ENTRY” and filed Aug. 31, 2015 and claimingpriority to U.S. Provisional Application No. 62/100,686, filed on Jan.7, 2015;

Ser. No. 14/841,288, entitled “MULTI-KEY ENCRYPTION METHOD” and filedAug. 31, 2015 and claiming priority to U.S. Provisional Application No.62/100,688, filed on Jan. 7, 2015;

Ser. No. 14/841,302, entitled “METHOD OF EPHEMERAL ENCRYPTEDCOMMUNICATIONS” and filed Aug. 31, 2015 and claiming priority to U.S.Provisional Application No. 62/100,689, filed on Jan. 7, 2015;

Ser. No. 14/841,292, entitled “METHOD OF MULTI-FACTOR AUTHENTICATIONDURING ENCRYPTED COMMUNICATIONS” and filed Aug. 31, 2015 and claimingpriority to U.S. Provisional Application No. 62/100,692, filed on Jan.7, 2015; and

Ser. No. 14/841,296, entitled “METHOD OF USING SYMMETRIC CRYPTOGRAPHYFOR BOTH DATA ENCRYPTION AND SIGN-ON AUTHENTICATION” and filed Aug. 31,2015 and claiming priority to U.S. Provisional Application No.62/100,693, filed on Jan. 7, 2015.

The content of the above applications are incorporated by reference intheir entirety.

BACKGROUND OF THE INVENTION Technical Field

The embodiments herein generally relate to cryptography, and, moreparticularly, to a system and method of cryptographically signing webapplications.

Description of the Related Art

Applications delivered through the Internet and executed with in auser's Internet browser (“browser”) are becoming increasing common onthe Internet. Often, such applications involve sensitive userinformation and may include, for example, credential information,payment information, and/or personal account management information. Forthese and other reasons, it is often desirous to verify that theapplication is an authentic copy and has not been tampered with in anyway. For example, sensitive user information could be severelycompromised by a malicious entity by modify an application to obtainsensitive user information and/or information from the user's computeror computer network. Moreover, when such a malicious entity tampers withthe application delivered through the Internet, the malicious entity mayalso be capable of tampering with the user's computer or other computerson the computer network.

To protect sensitive information, conventional methods often employ achallenge-response methodology, where, for example, an applicationdirects a user's browser to send an encrypted message that proves theuser knows some sensitive information (e.g., a password) withouttransmitting this required sensitive information.

The difficulties of such conventional methods for applications deliveredover the Internet and executed on a user's browser, however, arenumerous and publicly known. For example, when a challenge-responsemethod relies secret information to create an encrypted message and thesecret information is publicly known, the entire encryption systembecomes compromised and must be revised (e.g., resetting passwords,passphrases, private keys, etc.). Since various methods to obtain thissecret information are well known and frequently use—techniques such assuch as man-in-the-middle attacks, social engineering—it is thereforedesirable to reduce exposure to an encryption system's privateinformation when communication within a group and thereby reducing thepotential attack surface employing such an encryption system.

Additionally, as noted above, the application itself may have beentampered with and therefore not an authenticate copy. Conventionalmethods, such as the challenge-response methodology, do not address sucha situation and, significantly worse, create the illusion of a secureenvironment. It is therefore desirable to reduce exposure to anencryption system's private information and verify that an applicationobtained from the Internet and executed within a user's browser is anauthentic copy of that application.

BRIEF DESCRIPTION OF THE DRAWINGS

The embodiments herein will be better understood from the followingdetailed description with reference to the drawings, in which:

FIGS. 1A and 1B illustrate a flow diagram illustrating a method ofcryptographically signing web applications according to an embodimentherein;

FIG. 2 illustrates a schematic diagram of a network architecture used inaccordance with the embodiments herein; and

FIG. 3 illustrates a schematic diagram of a computer architecture usedin accordance with the embodiments herein.

DETAILED DESCRIPTION OF PREFERRED EMBODIMENTS

The embodiments herein and the various features and advantageous detailsthereof are explained more fully with reference to the non-limitingembodiments that are illustrated in the accompanying drawings anddetailed in the following description. Descriptions of well-knowncomponents and processing techniques are omitted so as to notunnecessarily obscure the embodiments herein. The examples used hereinare intended merely to facilitate an understanding of ways in which theembodiments herein may be practiced and to further enable those of skillin the art to practice the embodiments herein. Accordingly, the examplesshould not be construed as limiting the scope of the embodiments herein.

The embodiments herein provide a method of cryptographically signing webapplications. For example, a user (e.g., “Alice”) of an encryptedcommunication system (e.g., the Cyph™ secure messaging platform) wouldlike to use the encrypted communication system on a web browser toengage another user to the system (e.g., “Bob”) in encryptedcommunication. Using conventional methods, it is not possible for Aliceto verify that this application has not been tampered with. For example,according to conventional systems, Alice's browser automaticallydownloads the latest copy of the application code from the server everytime she navigates to the applications web address. Thus, according toconventional systems, very little security prevents a dedicated attackerfrom breaking into the application's server to tamper with the sourcecode (e.g., publish the secret information of a cryptographic system orsensitive user information) without either Alice or the Cyphadministrators noticing.

As described in further detail below, the system and method describedhere uses cryptographic signing to verify the integrity of anyapplication payload delivered over the Internet on the client-side,allowing Alice to know with certainty that the code her browser isexecuting was directly approved by an administrator of that application.Additionally, the embodiments herein are simple, in addition to beingmore secure and convenient, to implement compared to conventionalencrypted delivery systems

Referring now to the drawings, and more particularly to FIGS. 1 through3, where similar reference characters denote corresponding featuresconsistently throughout the figures, there are shown preferredembodiments.

FIGS. 1A and 1B illustrate a flow diagram illustrating a method 1 ofcryptographically signing web applications according to an embodimentherein. As shown in FIG. 1A, in step 10, When a user (i.e., Alice)navigates to the application's Web address (e.g., Cyph web address),instead of the server delivering the application itself, the serverdelivers a minimal bootstrap payload. The minimal bootstrap payload(“MBP”) is stored locally for as long as the client will allow(preferably the MBP is stored indefinitely). According to embodimentsherein, the MBP is locally stored using methods that include HTML5AppCache or HTTP Cache-Control headers. Moreover, according to oneembodiment herein, the MBP includes at least one public key and at leastone URL pointing to the latest application code payload. According toone embodiment herein, the application code payload includes anycombination of HyperText Markup Language (HTML), Cascading Style Sheets(CSS) and JavaScript (JS) (collectively known as HTML/CSS/JS), Androidapplication package (“APK”) and the like. Embodiments described herein,however, are not limited to such MBP and application code payloads.Rather the bootstrap and/or application code payloads described hereinbroadly includes any browser-supported programming language that supportlocal caching.

According to step 20, because the MBP has been cached locally, everytime the user opens the application's web address, the MBP is what willbe executed by the user's browser instead of what is delivered by theapplication's web address. Moreover, according to step 30, the firststep of the MBP is to download the latest version of the applicationcode from a URL specified in the MBP's configuration. The applicationcode targeted by that URL has previously been cryptographically signedusing a private key associated with a public key specified in thebootstrap payload's configuration. In step 40, the MBP then validatesthe cryptographic signature included with the application code. If thisis successful, the application code is executed normally. If it fails,the code is rejected. According to one embodiment herein, however, aprevious known good version may be optionally executed from localstorage/cache, if such a copy exists.

As a result of the method shown in FIG. 1A, all versions of theapplication run on a user's browser after the initial MBP was downloadedis cryptographically secure and validated, assuming the initial MBP wasvalid and untampered.

In addition to what is described above and shown in FIG. 1A, otherembodiments optionally may include several optimizations. For example,embodiments described herein may cache the latest known good version ofthe application code locally, both for performance reasons (to grab itfrom the cache in the event that it hasn't changed) and to fall back onin the event that verification of the application code ever fails in thefuture. Additionally, embodiments herein may further include at leastone URL pointing to a pre-computed hash of the latest application codein the bootstrap payload, and cryptographically sign those hashesinstead of the application payloads themselves (such that the clientneed only download a fresh copy of the hash to check for updates, ratherthan the entire application). According to such an embodiment, thebootstrap payload would then locally hash the unsigned application codeand compare the result to the signed hash in order to verify theapplication's integrity.

Additionally, as method 1 shown in FIG. 1A specifies “at least one URL”for the application code and hash, the bootstrap payload couldoptionally retry the download and verification steps with backup serversin the event that it fails on the first one (providing some additionalreliability to the system), and/or default to the geographically closestservers for performance reasons. Moreover, as method 1 shown in FIG. 1Aspecifies “at least one public key”, the bootstrap payload couldoptionally attempt to validate the signatures against more than oneindividual or organization's public key. Such an embodiment couldpotentially be evidence of a specific individual or organizationnegligence or malfeasance in the event that any particular version ofthe application code is later discovered to be malicious. Additionally,some programmatic environments permit to a local cache wipe remotelyfrom a server (e.g., HTML5 AppCache). To prevent such a local cache wipefrom a server, embodiments described herein may also include, in theMBP, detection of an attempt to local cache wipe from the server andwarn the user (e.g., by displaying a warning dialog box in the user'sbrowser).

FIG. 1B illustrates a schematic diagram illustrating cryptographicallysigning web applications according to an embodiment herein. As shownFIG. 1B, From a CDN node on the client's current continent, download thelatest signed hash and attempt to validate the signatures. If thefollowing conditions are met, replace signature data in local storagewith the new data: i) Signature verification was successful; ii) Hashexpiration date has not been passed; iii) Hash timestamp is more recentthan local known good hash timestamp; iv) User either does not havelocalStorage.webSignManualUpgrades set or consents to upgrade.Otherwise: leave local storage as-is. Moreover, if known good signaturedata exists in local storage: a) Download the current WebSign bootstrap,hash it with SHA256, and validate the hash against the whitelist fromthe local signature data; if there's no match, abort everything, panic,and show a warning message informing the user not to refresh or use Cyphagain; b) Validate that known good package hash isn't expired; c)Download the package from the CDN, with the query string set to the hashas a caching optimization; d) Compute SHA256 hash of package and compareit to known good package hash; if equal, execute the package viadocument.write. If no known good signature data exists in local storage,or if the above steps fail, retry against the default fallback continent(e.g., Europe). If that still fails, display, for example “Loading Cyphfailed. Please try again later.” In addition, while not shown in FIG.1B, For all WebSign bootstrap files according to one embodiment(including the AppCache manifest), apply: HTML AppCache; ServiceWorker;HTTP CacheControl public with max-age 1 year; HTTP Expires for December2037. While a single combined payload may be offer the simplestapproach, it is certainly possible to split the code into multiplefiles. In this case, additional verification logic is needed in thebootstrap payload described above (e.g., via separate signatures) or inthe signed application code (e.g., via pre-compute hashes)—potentiallytaking advantage of the upcoming Subresource Integrity standard of theWorld Wide Web Consortium (W3C). Additionally, for defense in depth, aserver-side HPKP key rotation scheme is employed wherein TLS keys pinnedin the users' browsers are periodically deleted and invalidated, thusexplicitly denying availability of our hostname after the first use, andforcing browsers to continue relying on the WebSign code they'doriginally cached.

FIG. 2 illustrates an implementation of an exemplary networkingenvironment (e.g., cloud computing environment 500) for the embodimentsdescribed herein is shown and described. The cloud computing environment500 may include one or more resource providers 502 a, 502 b, 502 c(collectively, 502). Each resource provider 502 may include computingresources. In some implementations, computing resources may include anyhardware and/or software used to process data. For example, computingresources may include hardware and/or software capable of executingalgorithms, computer programs, and/or computer applications. In someimplementations, exemplary computing resources may include applicationservers and/or databases with storage and retrieval capabilities. Eachresource provider 502 may be connected to any other resource provider502 in the cloud computing environment 500. In some implementations, theresource providers 502 may be connected over a computer network 508.Each resource provider 502 may be connected to one or more computingdevice 504 a, 504 b, 504 c (collectively, 504), over the computernetwork 508.

The cloud computing environment 500 may include a resource manager 506.The resource manager 506 may be connected to the resource providers 502and the computing devices 504 over the computer network 508. In someimplementations, the resource manager 506 may facilitate the provisionof computing resources by one or more resource providers 502 to one ormore computing devices 504. The resource manager 506 may receive arequest for a computing resource from a particular computing device 504.The resource manager 506 may identify one or more resource providers 502capable of providing the computing resource requested by the computingdevice 504. The resource manager 506 may select a resource provider 502to provide the computing resource. The resource manager 506 mayfacilitate a connection between the resource provider 502 and aparticular computing device 504. In some implementations, the resourcemanager 506 may establish a connection between a particular resourceprovider 502 and a particular computing device 504. In someimplementations, the resource manager 506 may redirect a particularcomputing device 504 to a particular resource provider 502 with therequested computing resource.

The techniques provided by the embodiments herein may be implemented onan integrated circuit chip (not shown). The chip design is created in agraphical computer programming language, and stored in a computerstorage medium (such as a disk, tape, physical hard drive, or virtualhard drive such as in a storage access network). If the designer doesnot fabricate chips or the photolithographic masks used to fabricatechips, the designer transmits the resulting design by physical means(e.g., by providing a copy of the storage medium storing the design) orelectronically (e.g., through the Internet) to such entities, directlyor indirectly. The stored design is then converted into the appropriateformat (e.g., GDSII) for the fabrication of photolithographic masks,which typically include multiple copies of the chip design in questionthat are to be formed on a wafer. The photolithographic masks areutilized to define areas of the wafer (and/or the layers thereon) to beetched or otherwise processed.

The resulting integrated circuit chips can be distributed by thefabricator in raw wafer form (that is, as a single wafer that hasmultiple unpackaged chips), as a bare die, or in a packaged form. In thelatter case the chip is mounted in a single chip package (such as aplastic carrier, with leads that are affixed to a motherboard or otherhigher level carrier) or in a multichip package (such as a ceramiccarrier that has either or both surface interconnections or buriedinterconnections). In any case the chip is then integrated with otherchips, discrete circuit elements, and/or other signal processing devicesas part of either (a) an intermediate product, such as a motherboard, or(b) an end product. The end product can be any product that includesintegrated circuit chips, ranging from toys and other low-endapplications to advanced computer products having a display, a keyboardor other input device, and a central processor.

The embodiments herein can take the form of an entirely hardwareembodiment, an entirely software embodiment or an embodiment includingboth hardware and software elements. The embodiments that areimplemented in software include but are not limited to, firmware,resident software, microcode, etc.

Furthermore, the embodiments herein can take the form of a computerprogram product accessible from a computer-usable or computer-readablemedium providing program code for use by or in connection with acomputer or any instruction execution system. For the purposes of thisdescription, a computer-usable or computer readable medium can be anyapparatus that can comprise, store, communicate, propagate, or transportthe program for use by or in connection with the instruction executionsystem, apparatus, or device.

The medium can be an electronic, magnetic, optical, electromagnetic,infrared, or semiconductor system (or apparatus or device) or apropagation medium. Examples of a computer-readable medium include asemiconductor or solid state memory, magnetic tape, a removable computerdiskette, a random access memory (RAM), a read-only memory (ROM), arigid magnetic disk and an optical disk. Current examples of opticaldisks include compact disk-read only memory (CD-ROM), compactdisk-read/write (CD-R/W) and DVD.

A data processing system suitable for storing and/or executing programcode will include at least one processor coupled directly or indirectlyto memory elements through a system bus. The memory elements can includelocal memory employed during actual execution of the program code, bulkstorage, and cache memories which provide temporary storage of at leastsome program code in order to reduce the number of times code must beretrieved from bulk storage during execution.

Input/output (I/O) devices (including but not limited to keyboards,displays, pointing devices, etc.) can be coupled to the system eitherdirectly or through intervening I/O controllers. Network adapters mayalso be coupled to the system to enable the data processing system tobecome coupled to other data processing systems or remote printers orstorage devices through intervening private or public networks. Modems,cable modem and Ethernet cards are just a few of the currently availabletypes of network adapters.

A representative hardware environment for practicing the embodimentsherein is depicted in FIG. 3. This schematic drawing illustrates ahardware configuration of an information handling/computer system 600 inaccordance with the embodiments herein. The system comprises at leastone processor or central processing unit (CPU) 610. The CPUs 610 areinterconnected via system bus 612 to various devices such as a randomaccess memory (RAM) 614, read-only memory (ROM) 616, and an input/output(I/O) adapter 618. The I/O adapter 618 can connect to peripheraldevices, such as disk units 611 and tape drives 613, or other programstorage devices that are readable by the system. The system can read theinventive instructions on the program storage devices and follow theseinstructions to execute the methodology of the embodiments herein. Thesystem further includes a user interface adapter 619 that connects akeyboard 615, mouse 617, speaker 624, microphone 622, and/or other userinterface devices such as a touch screen device (not shown) to the bus612 to gather user input. Additionally, a communication adapter 620connects the bus 612 to a data processing network 625, and a displayadapter 621 connects the bus 612 to a display device 623 which may beembodied as an output device such as a monitor, printer, or transmitter,for example.

For example, FIG. 3 includes exemplary embodiments of a computing deviceand a mobile computing device that can be used to implement thetechniques described in this disclosure. As a computing device, system600 is intended to represent various forms of digital computers, such aslaptops, desktops, workstations, personal digital assistants, servers,blade servers, mainframes, and other appropriate computers. As a mobilecomputing device, system 600 is intended to represent various forms ofmobile devices, such as personal digital assistants, cellulartelephones, smart-phones, and other similar computing devices. Thecomponents shown here, their connections and relationships, and theirfunctions, are meant to be examples only, and are not meant to belimiting.

Thus, as a computing device, system 600 includes a processor (e.g., CPUs610), a memory 614, storage units (e.g., ROM 616, disk units 611, tapedrives 613), a high-speed interface 618 connecting to the memory 614 andmultiple high-speed expansion ports 619, and a low-speed interface (notshown) connecting to a low-speed expansion port (not shown) and astorage device. Each of the processors, the memory 614, the storagedevice, the high-speed interface 618, the high-speed expansion ports619, and the low-speed interface, are interconnected using variousbusses (e.g., bus 612), and may be mounted on a common motherboard or inother manners as appropriate. The processor can process instructions forexecution within the computing device, including instructions stored inthe memory 614 or on the storage device to display graphical informationfor a GUI on an external input/output device, such as a display 623coupled to the high-speed interface 619. In other implementations,multiple processors and/or multiple buses may be used, as appropriate,along with multiple memories and types of memory. Also, multiplecomputing devices may be connected, with each device providing portionsof the necessary operations (e.g., as a server bank, a group of bladeservers, or a multi-processor system).

The memory 614 stores information within the computing device. In someimplementations, the memory 614 is a volatile memory unit or units. Insome implementations, the memory 614 is a non-volatile memory unit orunits. The memory 614 may also be another form of computer-readablemedium, such as a magnetic or optical disk.

The storage device is capable of providing mass storage for thecomputing device. In some implementations, the storage device may be orcontain a computer-readable medium, such as a floppy disk device, a harddisk device, an optical disk device, or a tape device, a flash memory orother similar solid state memory device, or an array of devices,including devices in a storage area network or other configurations.Instructions can be stored in an information carrier. The instructions,when executed by one or more processing devices (for example,processor), perform one or more methods, such as those described above.The instructions can also be stored by one or more storage devices suchas computer- or machine-readable mediums (for example, the memory 614,the storage device, or memory on the processor).

The high-speed interface 618 manages bandwidth-intensive operations forthe computing device, while the low-speed interface manages lowerbandwidth-intensive operations. Such allocation of functions is anexample only. In some implementations, the high-speed interface 618 iscoupled to the memory 614, the display 623 (e.g., through a graphicsprocessor or accelerator), and to the high-speed expansion ports 619,which may accept various expansion cards (not shown). In theimplementation, the low-speed interface is coupled to the storage deviceand the low-speed expansion port. The low-speed expansion port, whichmay include various communication ports (e.g., USB, Bluetooth®,Ethernet, wireless Ethernet) may be coupled to one or more input/outputdevices, such as a keyboard, a pointing device, a scanner, or anetworking device such as a switch or router, e.g., through a networkadapter.

The computing device may be implemented in a number of different forms,as shown in the figure. For example, it may be implemented as a standardserver, or multiple times in a group of such servers. In addition, itmay be implemented in a personal computer such as a laptop computer. Itmay also be implemented as part of a rack server system. Alternatively,components from the computing device may be combined with othercomponents in a mobile device (not shown), such as a mobile computingdevice. Each of such devices may contain one or more of the computingdevice and the mobile computing device, and an entire system may be madeup of multiple computing devices communicating with each other.

As a mobile computing device, system 600 includes a processor (e.g.,CPUs 610), a memory 614, an input/output device such as a display 623, acommunication interface 620, and a transceiver (not shown), among othercomponents. The mobile computing device may also be provided with astorage device, such as a micro-drive or other device, to provideadditional storage. Each of the processor, the memory 614, the display623, the communication interface 620, and the transceiver, areinterconnected using various buses (e.g., bus 612), and several of thecomponents may be mounted on a common motherboard or in other manners asappropriate.

The processor can execute instructions within the mobile computingdevice, including instructions stored in the memory 614. The processormay be implemented as a chipset of chips that include separate andmultiple analog and digital processors. The processor may provide, forexample, for coordination of the other components of the mobilecomputing device, such as control of user interfaces, applications runby the mobile computing device, and wireless communication by the mobilecomputing device.

The processor may communicate with a user through a control interface619 and a display interface (not shown) coupled to the display 623. Thedisplay 623 may be, for example, a TFT (Thin-Film-Transistor LiquidCrystal Display) display or an OLED (Organic Light Emitting Diode)display, or other appropriate display technology. The display interfacemay comprise appropriate circuitry for driving the display 623 topresent graphical and other information to a user. The control interface619 may receive commands from a user and convert them for submission tothe processor. In addition, an external interface (not shown) mayprovide communication with the processor, so as to enable near areacommunication of the mobile computing device with other devices. Theexternal interface may provide, for example, for wired communication insome implementations, or for wireless communication in otherimplementations, and multiple interfaces may also be used.

The memory 614 stores information within the mobile computing device.The memory 614 can be implemented as one or more of a computer-readablemedium or media, a volatile memory unit or units, or a non-volatilememory unit or units. An expansion memory (not shown) may also beprovided and connected to the mobile computing device through anexpansion interface (not shown), which may include, for example, a SIMM(Single In Line Memory Module) card interface. The expansion memory mayprovide extra storage space for the mobile computing device, or may alsostore applications or other information for the mobile computing device.Specifically, the expansion memory may include instructions to carry outor supplement the processes described above, and may include secureinformation also. Thus, for example, the expansion memory may be provideas a security module for the mobile computing device, and may beprogrammed with instructions that permit secure use of the mobilecomputing device. In addition, secure applications may be provided viathe SIMM cards, along with additional information, such as placingidentifying information on the SIMM card in a non-hackable manner.

The memory may include, for example, flash memory and/or NVRAM memory(non-volatile random access memory), as discussed below. In someimplementations, instructions are stored in an information carrier. Theinstructions, when executed by one or more processing devices (forexample, processor), perform one or more methods, such as thosedescribed above. The instructions can also be stored by one or morestorage devices, such as one or more computer- or machine-readablemediums (for example, the memory 614, the expansion memory, or memory onthe processor). In some implementations, the instructions can bereceived in a propagated signal, for example, over the transceiver orthe external interface.

The mobile computing device may communicate wirelessly through thecommunication interface 620, which may include digital signal processingcircuitry where necessary. The communication interface 620 may providefor communications under various modes or protocols, such as GSM voicecalls (Global System for Mobile communications), SMS (Short MessageService), EMS (Enhanced Messaging Service), or MMS messaging (MultimediaMessaging Service), CDMA (code division multiple access), TDMA (timedivision multiple access), PDC (Personal Digital Cellular), WCDMA(Wideband Code Division Multiple Access), CDMA2000, or GPRS (GeneralPacket Radio Service), among others. Such communication may occur, forexample, through the transceiver using a radio-frequency. In addition,short-range communication may occur, such as using a Bluetooth®, Wi-Fi™,or other such transceiver (not shown). In addition, a GPS (GlobalPositioning System) receiver module (not shown) may provide additionalnavigation- and location-related wireless data to the mobile computingdevice, which may be used as appropriate by applications running on themobile computing device.

The mobile computing device may also communicate audibly using an audiocodec, which may receive spoken information from a user and convert itto usable digital information. The audio codec may likewise generateaudible sound for a user, such as through a speaker (e.g., speaker 612or in a handset of the mobile computing device). Such sound may includesound from voice telephone calls, may include recorded sound (e.g.,voice messages, music files, etc.) and may also include sound generatedby applications operating on the mobile computing device.

The mobile computing device may be implemented in a number of differentforms, as shown in the figure. For example, it may be implemented as acellular telephone (not shown). It may also be implemented as part of asmart-phone, personal digital assistant, or other similar mobile device.

To provide for interaction with a user, the systems and techniquesdescribed here can be implemented on a computer having a display device(e.g., a CRT (cathode ray tube) or LCD (liquid crystal display) monitor)for displaying information to the user and a keyboard and a pointingdevice (e.g., a mouse or a trackball) by which the user can provideinput to the computer. Other kinds of devices can be used to provide forinteraction with a user as well; for example, feedback provided to theuser can be any form of sensory feedback (e.g., visual feedback,auditory feedback, or tactile feedback); and input from the user can bereceived in any form, including acoustic, speech, or tactile input.

The systems and techniques described here can be implemented in acomputing system that includes a back end component (e.g., as a dataserver), or that includes a middleware component (e.g., an applicationserver), or that includes a front end component (e.g., a client computerhaving a graphical user interface or a Web browser through which a usercan interact with an implementation of the systems and techniquesdescribed here), or any combination of such back end, middleware, orfront end components. The components of the system can be interconnectedby any form or medium of digital data communication (e.g., acommunication network). Examples of communication networks include alocal area network (LAN), a wide area network (WAN), and the Internet.

The computing system can include clients and servers. A client andserver are generally remote from each other and typically interactthrough a communication network. The relationship of client and serverarises by virtue of computer programs running on the respectivecomputers and having a client-server relationship to each other.

The foregoing description of the specific embodiments will so fullyreveal the general nature of the embodiments herein that others can, byapplying current knowledge, readily modify and/or adapt for variousapplications such specific embodiments without departing from thegeneric concept, and, therefore, such adaptations and modificationsshould and are intended to be comprehended within the meaning and rangeof equivalents of the disclosed embodiments. It is to be understood thatthe phraseology or terminology employed herein is for the purpose ofdescription and not of limitation. Therefore, while the embodimentsherein have been described in terms of preferred embodiments, thoseskilled in the art will recognize that the embodiments herein can bepracticed with modification within the spirit and scope of the appendedclaims.

What is claimed is:
 1. A method, comprising: receiving, at a client-sideweb browser, a minimal bootstrap payload from an application server;storing, by a client-side processor, the minimal bootstrap payload in aclient-side local cache, wherein the locally cached minimal bootstrappayload is executed by the client-side processor before executing anapplication from the application server; the minimal bootstrap payloadincludes at least one public key and at least one Uniform ResourceLocation (URL) address of an application code payload; the client-sideprocessor executes the minimal bootstrap payload, which comprises:receiving, at a client-side web browser, the application code payloadfrom the URL specified by the minimal bootstrap payload, wherein thereceived application code payload includes a cryptographic signatureusing a private key associated with the public key specified by theminimal bootstrap payload; verifying, by a client-side processor, thereceived application code payload cryptographic signature using thelocally stored public key; executing, by a client-side processor, thereceived application code payload after the received application payloadhas been successfully verified.